Skip to content

Conversation

@stainless-app
Copy link
Contributor

@stainless-app stainless-app bot commented Sep 24, 2025

Automated Release PR

0.11.3 (2025-09-24)

Full Changelog: v0.11.2...v0.11.3

Features


This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions


TL;DR

This is an automated release that bumps the package version to 0.11.3 and introduces a new feature for streaming logs on a per-invocation basis.

Why we made these changes

This change provides more granular observability into the system. By allowing users to access logs for a specific invocation, it becomes much easier to debug and monitor individual API calls without needing to sift through system-wide logs.

What changed?

  • Invocation Logs: Added functionality to the invocations resource to stream logs for a specific invocation.
  • API & Types: Updated API definitions, documentation (api.md), and parameter types (invocation_follow_params.py) to support the new feature.
  • Testing: Added new tests in test_invocations.py to validate the per-invocation logging functionality.
  • Version Bump: Updated the project version to 0.11.3 in pyproject.toml, CHANGELOG.md, and other release-related files.

Description generated by Mesa. Update settings

@stainless-app
Copy link
Contributor Author

stainless-app bot commented Sep 24, 2025

🧪 Testing

To try out this version of the SDK, run:

pip install 'https://pkg.stainless.com/s/kernel-python/8c116b6e8590709dab14961b7e9c038229f5ace5/kernel-0.11.2-py3-none-any.whl'

Expires: Fri, 24 Oct 2025 20:30:17 GMT

Copy link

@mesa-dot-dev mesa-dot-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Performed full review of 7030d45...c6ce4a9

Analysis

Based on the provided analysis, there do not appear to be any significant architectural issues with this pull request. The analysis shows that the implementation of the "Per Invocation Logs" functionality follows good practices and maintains consistency. The reviewer actually noted several strengths and no specific concerns with the implementation.

Since you specifically asked for potential issues, I'll note that the absence of identified problems in the architectural analysis suggests this is a well-executed change that doesn't introduce architectural risks.

Tip

⚡ Quick Actions

This review was generated by Mesa.

Actions:

Slash Commands:

  • /review - Request a full code review
  • /review latest - Review only changes since the last review
  • /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
  • /help - Get help with Mesa commands and configuration options

10 files reviewed | 0 comments | Review on Mesa | Edit Reviewer Settings

@hiroTamada hiroTamada changed the title release: 0.12.0 release: 0.11.3 Sep 24, 2025
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Sep 24, 2025

Release version edited manually

The Pull Request version has been manually set to 0.11.3 and will be used for the release.

If you instead want to use the version number 0.12.0 generated from conventional commits, just remove the label autorelease: custom version from this Pull Request.

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from c6ce4a9 to 291f434 Compare September 24, 2025 20:54
@stainless-app stainless-app bot merged commit 1d89a86 into main Sep 24, 2025
7 checks passed
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Sep 24, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants